The following table summarizes the various synchronization methods available in the SureSync program. A more detailed description of each rule type can be found by clicking on the name of the rule.
The “source” path for one-way rules is specified explicitly by the rule. For multi-way rules, the source path is the path with the latest version of a file. The “destination” is all other paths that are not the source path.
Add new files. Replace file on all other paths with a copy from source, if not yet identical.
If a file is deleted from any path...
The deleted file is recovered from another path. You must delete a file from all paths to prevent it from being recovered.
If a file changes on multiple paths... *
Issue warning and do not copy, unless the copy latest option was selected.
If a file is added to a path for the first time (SureSync has no history for the file)
Add new file.
If different versions of a file are added multiple paths (SureSync has no history for the file)
Issue warning and do not copy, unless the copy latest option was selected
If a file does not change on any path...
No action.
For Multi-way Rules, if a file has changed on more than one root and you have the "Resolve multiple updates with copy latest" option selected it will not warn you, and it will synchronize the files using the file with the most recent date to copy over the others. An exception will be recorded into the log.
For Multi-way Rules, you can handle files being updated in multiple locations with SureSync's file locking add-on. This add-on requires an additional license and also requires the use of the SPIAgent add-on. When file locking is used you eliminate the possibility of updates occuring to the same file on multiple sides of a synchronization. When a user opens a file with the file locking feature enabled that user will gain access to the file and all other copies of the file involved the synchronization will be locked until the user saves and closes the file. Any other user trying to access the file will receive a message informing them that the file is locked. This option eliminates the multiple file update issue entirely and is recommended for shares where users work off the same files frequently.
If you choose Skip as your synchronization method, any files specified in the skip Rule will not be processed in any Rule preceding the Skip rule.
If you choose Delete as your synchronization method, any files specified in the Rule will be deleted from whichever paths you choose.
For Multi-way Rules, you can handle files being updated in multiple locations with SureSync's file locking add-on. This add-on requires an additional license and also requires the use of the SPIAgent add-on. When file locking is used you eliminate the possibility of updates occuring to the same file on multiple sides of a synchronization. When a user opens a file with the file locking feature enabled that user will gain access to the file and all other copies of the file involved the synchronization will be locked until the user saves and closes the file. Any other user trying to access the file will receive a message informing them that the file is locked. This option eliminates the multiple file update issue entirely and is recommended for shares where users work off the same files frequently.